Update Cabal and Cabal-syntax bounds to permit cabal 3.18#339
Merged
Conversation
Contributor
|
Queued — the merge queue status continues in this comment ↓. |
Member
Author
|
I hope this is not controversial, so let me merge without reviews. |
Contributor
Merge Queue Status
This pull request spent 14 seconds in the queue, including 1 second running CI. Required conditions to merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It would be good to release a new hackage-security version to Hackage once this PR is merged, to test cabal 3.18 with it before the cabal 3.18 release.
@andreasabel: would you like to do the release, as you did last time, or shall I?